View INTEL82802AC_7949527.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

intel ? 82802ab/82802ac firmware hub (fwh) datasheet november 2000 document number: 290658-004 r
intel ? 82802ab/ac firmware hub r 2 datasheet information in this document is provided in connection with intel products. no license, express or implied, by estoppel or oth erwise, to any intellectual property rights is granted by this document. except as provided in intel?s terms and conditions of sale for such products, inte l assumes no liability whatsoever, and intel disclaims any express or implied warranty, relating to sale and/or use of intel products including liabil ity or warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent, copyright or other intellectual property right. intel products are not intended for use in medical, life saving, or life sustaining applications. intel may make changes to specifications and product descriptions at any time, without notice. designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined." int el reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. the intel ? 82802ab/ac firmware hub (fwh) may contain design defects or errors known as errata which may cause the product to deviate from published specifications. current characterized errata are available on request. contact your local intel sales office or your distributor to obtain the latest specifications and before placing your product o rder. i 2 c is a 2-wire communications bus/protocol developed by philips. smbus is a subset of the i 2 c bus/protocol and was developed by intel. implementations of the i 2 c bus/protocol may require licenses from various entities, including philips electronics n.v. and north american philips corpor ation. a lert on lan is a result of the intel-ibm advanced manageability alliance and a trademark of ibm copies of documents which have an ordering number and are referenced in this document, or other intel literature, may be obtain ed from: intel corporation www.intel.com or call 1-800-548-4725 *third-party brands and names are the property of their respective owners. copyright ? intel corporation 1999-2001
intel ? 82802ab/ac firmware hub r datasheet 3 contents 1. architectural overview ......................................................................................................... ........ 9 1.1. interface overview........................................................................................................... 9 1.1.1. intel firmware hub interface....................................................................... 10 1.1.2. address/address-multiplexed interface ...................................................... 10 1.2. nonvolatile flash memory core .................................................................................... 10 2. pinout configurations .......................................................................................................... ....... 13 2.1. pin descriptions............................................................................................................. 14 3. interface operation description ................................................................................................ .17 3.1. read 17 3.2. write 17 3.3. output disable............................................................................................................... 17 3.4. reset 17 3.5. operational effects of hardware write-protect pins tbl# and wp# ........................... 18 4. functional descriptions........................................................................................................ ...... 19 4.1. read array command................................................................................................... 21 4.2. read identifier codes command .................................................................................. 21 4.3. read status register command................................................................................... 21 4.4. clear status register command................................................................................... 21 4.5. block erase command ................................................................................................. 22 4.6. program command....................................................................................................... 22 4.7. block erase suspend command .................................................................................. 23 4.8. program suspend comand........................................................................................... 23 4.9. register based locking, general-purpose input, and random number generator registers 23 4.9.1. t_block_lk and t_minusxx_lk ? block-locking registers ............... 25 4.9.2. general-purpose input register ................................................................. 26 4.9.2.1. gpi_reg ? general-purpose input register ............................... 26 4.9.3. random number generator registers ....................................................... 27 4.9.3.1. rng hardware status register ..................................................... 27 4.9.3.2. rng data status register ............................................................. 27 4.9.3.3. rng data register......................................................................... 28 4.10. using the random number generator ......................................................................... 28 4.11. detecting and initializing the rng device..................................................................... 28 4.11.1. detecting the rng device .......................................................................... 28 4.11.2. initializing the rng device.......................................................................... 29 4.11.3. selecting appropriate fwh ids and densities ........................................... 29 4.11.4. mapping fwh devices onto memory map ................................................. 30 4.11.5. paging fwh devices for greater than 4 mb of fwh memory ................. 30 4.11.6. programming multiple fwh devices .......................................................... 30 4.12. cui automation flowcharts........................................................................................... 31 5. electrical specifications ...................................................................................................... ....... 33 5.1. absolute maximum ratings........................................................................................... 33
intel ? 82802ab/ac firmware hub r 4 datasheet 5.2. operating conditions .....................................................................................................33 5.2.1. interface dc input/output specifications ....................................................34 5.2.2. interface ac input/output specifications.....................................................36 5.2.3. intel fwh interface ac timing specifications ............................................37 5.2.3.1. clock specification..........................................................................37 5.2.3.2. signal timing parameters...............................................................38 5.3. block programming times ............................................................................................40 5.4. intel firmware hub interface..........................................................................................40 5.4.1. intel fwh interface cycles..........................................................................40 5.4.1.1. read cycle sequence.....................................................................40 5.4.1.2. single-byte read waveforms.........................................................42 5.4.1.3. write cycle sequence.....................................................................42 5.4.1.4. write waveforms ............................................................................43 5.4.1.5. response to invalid fields.............................................................43 5.4.1.6. abort operations .............................................................................44 5.4.1.7. intel fwh cycle timing information ...............................................44 5.5. rng parameters ...........................................................................................................45 6. prom programming specifications ...........................................................................................47 6.1. programming (?a/a mux?) mode operation ...................................................................47 6.2. bus operation ................................................................................................................47 6.2.1. output disable/enable.................................................................................47 6.2.2. row/column addresses ..............................................................................47 6.2.3. read operation ...........................................................................................47 6.2.4. read identifier codes operation .................................................................48 6.2.5. write operation ...........................................................................................48 6.3. command definitions ....................................................................................................48 6.4. electrical characteristics in a/a mux mode ...................................................................48 6.4.1. reset operations.........................................................................................49 6.4.2. ac waveforms for reset operations ..........................................................49 6.4.3. a/a mux read-only operations (1,3) .............................................................49 6.4.4. a/a mux write operations (1,2) .....................................................................51
intel ? 82802ab/ac firmware hub r datasheet 5 figures figure 1. simplified block diagram ..................................................................................... 8 figure 2. device memory map with intel fwh hardware lock architecture .................... 11 figure 3. intel fwh boot-configuration system memory map......................................... 11 figure 4. 32-lead plcc intel firmware hub pinout......................................................... 13 figure 5. 40-lead tsop intel firmware hub pinout ........................................................ 13 figure 6. automated block erase flowchart..................................................................... 31 figure 7. clock waveform ................................................................................................ 37 figure 8. output timing parameters................................................................................. 38 figure 9. input timing parameters ................................................................................... 39 figure 10. fwh single-byte read waveforms .................................................................. 42 figure 11. write waveforms ............................................................................................... 43 figure 12. intel fwh output timing parameters ............................................................... 45 figure 13. intel fwh input timing parameters .................................................................. 46 figure 14. a/a mux read timing diagram ......................................................................... 50 figure 15. a/a mux write timing diagram ......................................................................... 52 tables table 1. pin descriptions ................................................................................................. 14 table 2. command definitions......................................................................................... 19 table 3. status register definition .................................................................................. 20 table 4. identifier codes .................................................................................................. 21 table 5. intel firmware hub register configuration map................................................ 24 table 6. register-based locking value definitions......................................................... 25 table 7. temperature and vcc....................................................................................... 33 table 8. intel fwh interface dc input/output specifications.......................................... 34 table 9. power supply specifications ? all interfaces ................................................... 35 table 10. intel fwh interface ac input/output specifications.......................................... 36 table 11. clock specification............................................................................................. 37 table 12. signal timing parameters.................................................................................. 38 table 13. interface measurement condition parameters .................................................. 39 table 14. ac waveform for reset operation.................................................................... 39 table 15. programming times .......................................................................................... 40 table 16. fwh read cycle ............................................................................................... 41 table 17. fwh write cycle ............................................................................................... 42 table 18. signal timing parameters.................................................................................. 44 table 19. rng timing characteristics .............................................................................. 45 table 20. rng statistical characteristics.......................................................................... 45 table 21. bus operations .................................................................................................. 48
intel ? 82802ab/ac firmware hub r 6 datasheet revision history rev. draft/changes date -001 ? initial release april 1999 -002 ? added chapter 6 ? updated programmer vendor/service provider information. may 1999 -003 ? changed v ih min. spec to reflect actual value. ? updated programmer vendor/service provider information. ? clarification of part numbering. ? spec now includes all known issues from all densities/lithographies. ? included fwh memory cycle and rng information. may 2000 -004 ? removed all references to multi-byte read cycles ? added dc characteristics for a/a mux mode november 2000
intel ? 82802ab/ac firmware hub r datasheet 7 intel ? 82802ab/ac firmware hub (fwh) product features intel platform compatability ? enables security-enhanced platform infrastructure; facilitates option to remove isa. firmware hub hardware interface mode ? 5-signal communication interface supporting byte-at-a-time reads and writes ? register-based read and write protection for each code/data storage block ? hardware write protect pins for the top boot block and the remaining code/data storage blocks ? 5 additional gpis for platform design flexibility ? contains a hardware random number generator (rng) for enhancing platform security ? integrated command user interface (cui) for requesting access to locking, programming, and erasing options. the cui also handles requests for data residing in status, id, and block-lock registers. ? operates with 33-mhz pci clock and 3.3 v i/o. industry-standard packages (40l tsop or 32l plcc) two configurable interfaces ? firmware hub interface for platform operation ? address/address-multiplexed (a/a mux) interface for programming during manufacturing 4 or 8 mbits of flash memory for platform code/data nonvolatile storage ? symmetrically blocked, 64-kb memory sections ? available in 8-mbit (intel ? 82802ac) and 4- mbit (intel ? 82802ab) densities ? automated byte program and block erase via an integrated write state machine (wsm) address/address-multiplexed (a/a mux) interface/mode ? 11-pin multiplexed address and 8-pin data i/o interface ? supports fast on-board or out-of-system programming for manufacturing case temprature operating range power supply specifications ? vcc: 3.3 v 0.3 v ? vpp: 3.3 v and 12 v for fast programming, (80 hours maximum) the intel ? 82802 (fwh) firmware hub may contain design defects or errors known as errata that may cause the products to deviate from published specifications. current characterized errata are available upon request.
intel ? 82802ab/ac firmware hub r 8 datasheet figure 1. simplified block diagram processor ac?97 codec(s) (optional) lpc interface pci agent pci bus pci slot super i/o keyboard, mouse, fd, pp, sp, ir memory ide (4 drives) smbus ide ac?97 usb smbus device(s) gpio memory controller i/o controller 82802 isa bridge (optional)
intel ? 82802ab/ac firmware hub r datasheet 9 1. architectural overview the intel ? 82802 firmware hub (fwh) discrete component is compatible with several intel chipset platforms and a variety of applications. the device operates under the lpc/fwh interface/protocol. the hardware features of this device include a random number generator (rng), five general-purpose inputs (gpis), register-based block locking, and hardware-based locking. this combination of logic features and non-volatile memory enables better protection for the storage and update of platform code and data, adds platform flexibility through additional gpis, and allows for quicker introduction of new security/manageability features into current and future platforms. the platform rng, accessed through the intel ? security driver and third-party software, enables security features for the pc platform. see the product features listed previously for a list of more key features that the intel fwh provides. 1.1. interface overview this device is equipped with two hardware interfaces. the state of the device?s ?ic? (interfaceconfiguration) pin determines which interface is in use. the interface mode must be selected prior topower-up or before return from reset (rst# or init# low-to-high transition). the intel fwh interface isdesigned to work with the intel family of i/o controller hubs (ich) during platform operation. the a/a mux interface is designed as a programming interface for oems, for use during motherboard manufacturing or component pre-programming. the a/a mux interface is not intended for use during regular personal computer operation. such a configuration would cause the expected (intel fwh) interface to be disabled, and the system boot sequence would fail upon power-up. an internal command user interface (cui) serves as the internal control center for the nonvolatilememory core in either of the two device interfaces (intel fwh or a/a mux). a single valid commandsequence written to the cui initiates an automated sequence of internal events to complete various tasks. an internal write state machine (wsm) automatically executes the algorithms and timings necessary for block erase and program operations. driving rst# or init# low resets the device, which resets the block-lock registers to their default (write-locked) condition and clears the status register. a reset time (tphqv a/a mux) is required from rst# or init# switching high until outputs are valid. likewise, the device has a wake time (tphrh a/a mux) from rst# or init# high until writes to the cui are recognized. a reset latency will occur if a reset procedure is performed during a programming or erase operation. resetting the component will put the component back into read-array mode. note: there is no chip enable (like ce#) in either interface. stand-by current control in the inel fwh interface is enabled automatically, if the intel fwh4 is high and the device is not working to complete a requested activity.
intel ? 82802ab/ac firmware hub r 10 datasheet 1.1.1. intel firmware hub interface the intel firmware hub (intel fwh) interface consists primarily of a 5-signal communication interface used to control the operation of the device in a system environment. the buffers for this interface were designed to be pci compliant. to ensure the effective delivery of security and manageability features, the intel fwh interface is the only way access the full feature set of the device. the intel fwh interface is equipped to operate at 33 mhz, synchronous with the pci bus. 1.1.2. address/address-multiplexed interface the a/a mux refers to the multiplexed row and column addresses in this interface. this approach is required so that the device can be tested and programmed quickly with automated test equipment (ate) or off-board prom programmers in the oem?s manufacturing flow. this interface also allows the device to have an efficient programming interface with potentially large future densities, while still fitting into a 32-pin package. only basic reads, programming, and erasure of the nonvolatile memory blocks can be performed through the a/a mux interface. in this mode, the intel fwh features, security features, and registers are unavailable. a row/column (r/c#) pin determines which set of addresses (rows or columns) is latched. see the a/a mux pin description table for more information. 1.2. nonvolatile flash memory core the primary feature of the intel fwh component is a nonvolatile memory core based on intel ? flash technology. this high-performance memory array is arranged in eight (4-mbit device) or sixteen (8- mbit device) 64-kb blocks. intel ? flash technology enables fast factory programming and low-power designs. specifically designed for 3-v systems, this component supports read operations at 3.3 v v cc and block erase and program operations at 3.3 v and 12 v v pp . the 12 v v pp option yields the fastest program performance, which will increase factory throughput, but is not recommended for standard in-system fwh operation in the platform, due to an 80-hr limit for 12 v on the v pp pin over the lifetime of the device, whether or not programming is taking place. with the 3.3-v v pp option (recommended for in-system operation), v cc and v pp may be tied together for a simple, low-power 3-v design. in addition to the voltage flexibility, the dedicated v pp pin provides complete data protection when v pp v pplk . internal v pp detection circuitry automatically configures the device for block erase and program operations. while current for 12-v programming will be drawn from v pp , 3.3-v programming solutions should design their board such that v pp draws from the same supply as v cc , and should assume that full programming current may be drawn from either pin.
intel ? 82802ab/ac firmware hub r datasheet 11 figure 2. device memory map with intel fwh hardware lock architecture 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 64-kbyte block 64-kbyte block 64-kbyte block 64-kbyte block 64-kbyte block 64-kbyte block 64-kbyte block 64-kbyte block 64-kbyte block 64-kbyte block 64-kbyte block 64-kbyte block 64-kbyte block 64-kbyte block 64-kbyte block 64-kbyte block } tbl# (8 mb) } tbl# (4 mb) wp# (8 mb) blocks 0-14 wp# (4 mb) mem_map_lock 0fffff 0f0000 0effff 0e0000 0dffff 0d0000 0cffff 0c0000 0bffff 0b0000 0affff 0a0000 09ffff 090000 08ffff 080000 07ffff 070000 06ffff 060000 05ffff 050000 04ffff 040000 03ffff 030000 02ffff 020000 01ffff 010000 00ffff 000000 figure 3. intel fwh boot-configuration system memory map sys_memmap_boot system memory (top 4 mb) fff80000h ffffffffh fff00000h ffc00000h fwh 4 mbit fwh 8 mbit block 7 block0 block 15 block 0 range for other fwh devices
intel ? 82802ab/ac firmware hub r 12 datasheet this page is intentionally left blank.
intel ? 82802ab/ac firmware hub r datasheet 13 2. pinout configurations figure 4. 32-lead plcc intel firmware hub pinout intelfirmware hub (intelfwh) 32-lead plcc 0.450" x 0.550" top view rst# vpp 32 31 30 29 28 27 26 25 24 23 22 21 20 19 17 18 1 2 3 4 5 6 7 8 9 10 11 12 13 14 16 15 clk vcc fwh2 gnd fwh3 fwh1 fwh0 id0 id1 id2 id3 fgpi2 fgpi3 fgpi4 rfu rfu rfu fgpi1 fgpi0 wp# tbl# a/a mux a/a mu x a/a mu x a/a mux we# ic(v ih ) dq7 ry/by# oe# gnda vcca gnd vcc a5 vpp a6 a4 vcc dq2 gnd dq3 dq6 dq1 dq5 dq4 dq0 r/c# rst# a10 a9 a8 a7 a3 a2 a1 a0 fwh4 rfu gnda gnd vcca ic (v il ) init# vcc rfu figure 5. 40-lead tsop intel firmware hub pinout rst# nc nc nc nc nc vcc vpp vcca fwh4 init# gnd gnd rfu rfu rfu id0 id1 id2 id3 fwh2 fwh3 fwh1 fwh0 vcc rfu 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 40 39 38 37 36 35 34 33 nc firmware hub (fwh) 40-lead tsop 10mm x 20mm top view clk nc wp# tbl# fgpi4 ic (v il ) gnda nc rfu we# nc nc nc ic (v ih ) nc nc a10 nc nc a9 a8 a7 a6 a5 a4 vcc vpp vcca rst# oe# ry/by# gnd gnd dq6 dq7 dq5 a0 a1 a2 a3 dq2 dq3 dq1 dq0 gnda vcc dq4 nc r/c# a/a mux a/a mux fgpi0 fgpi1 fgpi2 fgpi3
intel ? 82802ab/ac firmware hub r 14 datasheet 2.1. pin descriptions the pin descriptions table details the usage of each device pin. most pins have dual functionality, with functions in both the intel firmware hub and a/a mux interfaces. the a/a mux functionality for pins is shown bold italic in the description box for that pin. all pins are designed to be compliant with vcc + 0.3 v max. unless otherwise noted. table 1. pin descriptions interface symbol type intel fwh a/a mux name and function ic i x x interface configuration pin. this pin determines which interface is used to communicate with the device. when it is held low, the intel fwh interface is enabled. when it is held high, the a/a mux interface is enabled. this pin must be set at power-up or before return from reset, and must not be changed during device operation. this pin is pulled down with an internal resistor of between 20 and 100 k ? . when the ic is high (a/a mux mode), this pin will exhibit a leakage current of approximately 200 a. this pin may be floated, which will select the intel fwh mode. rst# i x x interface reset. valid for both a/a mux and intel fwh interface operation. when driven low, rst# inhibits write operations to provide data protection during power transitions, resets internal automation, and tri-states pins fwh[3:0] (in intel fwh interface mode). rst#-high enables normal operation. when exiting from reset, the device defaults to read array mode. init# i x processor reset. this is a second reset pin for in-system use. this pin is internally combined with the rst# pin. if this pin or rst# is driven low, identical operation is exhibited. this signal is designed to be connected to the chipset init signal (max. voltage depends on the processor. do not use 3.3 v). a/a mux = oe# clk i x 33-mhz clock for intel fwh interface. this input is the same as that for the pci clock and adheres to the pci specification. a/a mux = r/c# fwh[3:0] i/o x intel fwh i/os. i/o communication a/a mux = dq[3:0] fwh4 i x intel fwh input. input communication a/a mux = we#
intel ? 82802ab/ac firmware hub r datasheet 15 interface symbol type intel fwh a/a mux name and function id[3:0] i x identification inputs. these four pins are part of the mechanism that allows multiple parts to be attached to the same bus. the strapping of these pins is used to identify the component. the boot device must have id[3:0] = 0000, and it is recommended that all subsequent devices use sequential up-count strapping ( 0001, 0010,0011,... ). these pins are pulled down with internal resistors, with values between 20 and 100 k ? , when in the intel fwh mode. any id pins pulled high will exhibit a leakage current of approximately 200 a. any pins intended to be low may be left to float. in a single intel fwh system, all may be left floating. a/a mux = a[3:0] fgpi[4:0] i x intel fwh general purpose inputs. these individual inputs can be used for additional board flexibility. the state of these pins can be read immediately at boot, through intel fwh registers. these inputs should be at their desired state before the start of the pci clock cycle during which the read is attempted, and they should remain at the same level until the end of the read cycle. they may only be used for 3.3-v signals. unused fgpi pins must not be floated. a/a mux = a[10:6] tbl# i x top block lock. when low, it prevents programming or block erase to the highest addressable block (7 in a 4-mbit, 15 in an 8-mbit component), regardless of the state of the lock register. tbl#-high disables hardware write protection for the top block, though register- based protection still applies. the status of tbl# does not affect the status of block-locking registers. a/a mux = a4 wp# i x write protect. when low, prevents programming or block erase to all but the highest addressable block (0-6 in a 4-mbit, 0-14 in an 8- mbit component), regardless of the state of the corresponding lock registers. wp#-high disables hardware write protection for these blocks, t hough register-based protection still applies. the status of tbl# does not affect the status of block-locking registers. a/a mux = a5 a[0:10] i x low-order address inputs. inputs for low-order addresses during read and write operations. addresses are internally latched during a write cycle. for the a/a mux interface, these addresses are latched by r/c# and share the same pins as the high-order address inputs. dq[0:7] i/o x data input/outputs. these pins receive data and commands during cui write cycles and transmit data during memory array, status register, and identifier code read cycles. data pins float to high impedance when outputs are disabled. data is internally latched during a write cycle. oe# i x output enable. gates the device?s outputs during a read cycle r/c# i x row-column address select. for the a/a mux interface, this pin determines whether the address pins are pointing to the row addresses (a[0:10]) or the column addresses (a[11:19]). we# i x write enable. controls writes to the cui and array blo cks. addresses and data are latched on the rising edge of the we# pulse.
intel ? 82802ab/ac firmware hub r 16 datasheet interface symbol type intel fwh a/a mux name and function v pp pwr x x block erase/program power supply. for erasing array blocks or programming data. v pp = 3.3 v or 12 v v pp . with v pp v pplk , memory contents cannot be altered. attempting a block erase or program with an invalid v pp (see dc characteristics) will produce spurious results and should not be attempted. v pp may only be held at 12 v for 80 hours over the lifetime of the device. v cc pwr x x device power supply. internal detection automatically configures the device for optimized read performance. do not float any power pins. with v cc v lko , all attempts to write to flash memory are inhibited. device operations at invalid v cc voltages (see dc characteristics) produce spurious results and should not be attempted. gnd pwr x x ground. do not float any ground pins. v cca pwr x x analog power supply. this supply should share the same system supply as v cc . gnd a pwr x x analog ground. should be tied to same plane as gnd. rfu x reserved for future use. these pins are reserved for future generations of this product. they may be left disconnected or driven. if they are driven, the voltage levels should satisfy v ih and v il requirements. a/a mux = dq[7:4] nc x x no connect. pin may be driven or floated. if it is driven, the voltage levels should satisfy v ih and v il . no connects appear only on the 40ld tsop package. ry/by# 0 x ready/busy. valid only in a/a mux mode. this output pin is a reflection of bit 7 in the status register. this pin is used to determine block erase or program completion.
intel ? 82802ab/ac firmware hub r datasheet 17 3. interface operation description 3.1. read memory information, identifier codes, gpi registers or the status register can be read, regardless of the v pp voltage. commands using the read mode include: reading memory from the array, reading the identifier codes, reading the status register, reading the lock bit registers, reading the random number generator, reading the gpi registers, and reading the rng status register. upon initial device power-up or after exit from reset, the device automatically resets to read array mode. 3.2. write writes to the memory array?s cui are initiating by issuing a write through the intel fwh interface. (see the following information on timing and intel fwh cycle write protocol specifics.) the cui does not occupy a single, specific memory location?any valid address may be given. however, certain commands, such as block erase, require the address be within the range of the desired address block. 3.3. output disable when the intel fwh is not selected through a fwh read or write cycle, the intel fwh interface outputs (fwh[3:0]) are disabled and is placed in a high-impedance state. 3.4. reset rst# or init# at v il initiates a device reset. in the read mode, rst# or init# low deselects the memory, places output drivers in a high-impedance state, and turns off all internal circuits. rst# or init# must be held low for time t plph (a/a mux and fwh operation). the intel fwh resets to read array mode upon return from reset, and all blocks are set to default (locked) status (see 4.9.1), regardless of their locked state prior to reset. during block erase or program, driving rst# or init# low will abort the operation underway, in addition to causing a reset latency. memory contents being altered are no longer valid, since the data may be partially erased or programmed. it is important to assert rst# or init# during system reset. when the system comes out of reset, it will expect to read from the memory array of the device. if a system reset occurs with no fwh reset?this is hardware dependent?it is possible that proper processor initialization will not occur. (the intel fwh memory may be providing status information instead of memory array data.)
intel ? 82802ab/ac firmware hub r 18 datasheet 3.5. operational effects of hardware write-protect pins tbl# and wp# the tbl# and wp# pins on the intel fwh provide hardware write protect capabilities. the top block lock (tbl#) pin, when held low (active), prevents program or block erase operations in the top-most block of the device where critical code can be stored. when tbl# is high, hardware write protection of the top block is disabled. the write protect (wp#) pin has a function similar to tbl#, but affects all remaining blocks. wp# operates independently from tbl# and does not affect the lock status of the top block. the tbl# and wp# pins must be set to the desired protection state prior to starting a program or erase operation, since they are sampled at the beginning of the operation. changing the state of tbl# or wp# during a program or erase operation may cause unpredictable results. if the state of tbl# or wp# changes during a program suspend or erase suspend state, the changes to the device?s locking status do not take place immediately. the suspended operation may be resumed to successfully complete the program or erase operation. the new lock status will take place after the program or erase operation completes. these pins function in combination with the register-based block locking described in section 4.9. when active, these pins write-protect the appropriate block(s), regardless of the associated block-locking registers. (for example, when tbl# is active, writing to the top block is prevented, regardless of the state of the write-lock bit for the top block?s locking register. in such a case, clearing the write-protect bit in the register will have no functional effect, even though the register may indicate that the block is no longer locked. the register may still be set to read-lock the block, if desired.) see section 4.9 for further information.
intel ? 82802ab/ac firmware hub r datasheet 19 4. functional descriptions when the v pp voltage v pplk , read operations from the status register, identifier codes or memory are enabled, but programming and erase functions are disabled. placing v pph1/2 on v pp enables successful block erase and program operations. table 2. command definitions first bus cycle second bus cycle command bus cycles required notes oper. addr. (1) data (2) oper. addr. (1) data (2) read array/reset 1 write x ffh read identifier codes 2 2 write x 90h read ia id read status register 2 write x 70h read x srd clear status register 1 write x 50h block erase 2 3 write ba 20h write ba d0h program 2 3,4 write wa 40h or 10h write wa wd block erase and program suspend 1 3 write x b0h block erase and program resume 1 3 write x d0h note: 1. key: x = any valid address within the device ia = identifier code address ba = address within the block being erased wa = address of memory location to be written srd = data read from status register. wd = data to be written at location wa id = data read from identifier codes 2. following the read identifier codes command, read operations access manufacturer and device. see table 4 for the read identifier code data. 3. the block must not be write locked when attempting block erase or program operations. attempts to issue a block erase or program to a write-locked block will fail. 4. either 40h or 10h are recognized by the wsm as the program setup. note: commands other than those shown previously are reserved by intel for future device implementations and should not be used.
intel ? 82802ab/ac firmware hub r 20 datasheet table 3. status register definition 7 6 5 4 3 2 1 0 wsms ess es ps vpps pss dps r bit description 7 write state machine status (sr.7). check sr.7 to determine block erase or program completion. sr.6?0 are invalid while sr.7 = 0. 1 = ready 0 = busy 6 erase suspend status (sr.6). 1 = block erase suspended 0 = block erase in progress/completed 5 erase status (sr.5). if both sr.5 and sr.4 are 1s after a block erase attempt, an improper command sequence was entered. 1 = error in block erasure 0 = successful block erase 4 program status (sr.4). 1 = error in program 0 = successful program 3 v pp status (sr.3). sr.3 does not provide a continuous indication of v pp level. the wsm interrogates and indicates the v pp level only after a block erase or program operation. sr.3 is not guaranteed to reports accurate feedback only when v pp v pph1/2 . 1 = v pp low detect, operation abort 0 = v pp ok 2 program suspend status (sr.2). 1 = program suspended 0 = program in progress/completed 1 device protect status (sr.1). sr.1 does not provide a continuous indication of write-lock bit, tbl# pin or wp# pin values. the wsm interrogates the write-lock bit, tbl# pin or wp# pin only after a block erase or program operation. depending on the attempted operation, it informs the system whether or not the selected block is locked. 1 = write-lock bit, tbl# pin, or wp# pin detected, operation abort 0 = unlock 0 reserved for future enhancements (sr.0). sr.0 is reserved for future use and should be masked out when polling the status register.
intel ? 82802ab/ac firmware hub r datasheet 21 4.1. read array command upon initial device power-up and after exit from reset, the device defaults to the read array mode. this operation can also be initiated by writing the read array command. the device remains available for array reads until another command is written. once the internal write state machine (wsm) has started a block erase or program, the device will not recognize the read array command until the operation is completed, unless the operation is suspended via an erase suspend or program suspend command. the read array command functions independently of the v pp voltage. 4.2. read identifier codes command the identifier code operation is initiated by writing the read identifier codes command. following the write of the command, the device will read back the (manufacturer and device) id data from the addresses shown in the following table. to terminate the read identifier code operation, write another valid command to the intel fwh. the read identifier codes command functions independently of the v pp voltage. table 4. identifier codes code address data manufacturer code 000000 89 device code 4 mbit 000001 ad device code 8 mbit 000001 ac 4.3. read status register command the status register may be read to determine when a block erase or program completes, and whether the operation completed successfully. the status register may be read at any time by writing the read status register command. after writing this command, all subsequent read operations will return data from the status register until another valid command is written. the read status register command functions independently of the v pp voltage. 4.4. clear status register command error flags in the status register can only be set to 1s by the wsm and can only be reset by the clear status register command. these bits indicate various conditions that may cause failure. the clear status register command functions independently of the applied v pp voltage.
intel ? 82802ab/ac firmware hub r 22 datasheet 4.5. block erase command the erase command operates on one block at a time. this command requires an (arbitrary) address within the block to be erased. recall that erasure changes all block data to ffh. block preconditioning, erase, and erase verify are handled internally by the wsm, which is transparent to the system. after issuing the erase command, the device automatically outputs status register data when read. when the block erase completes, the status register may be checked. if the fwh detects a block erase error, the status register should be cleared before system software attempts corrective actions. after a block erase, the cui remains in read status register mode until a new command is issued. successful block erasure requires that the corresponding block?s write-lock-bit is cleared, and the corresponding write-protect pin (tbl# or wp#) is inactive. if a block erase is attempted when the block is locked, the block erase will fail, with the reason for failure in the status register. successful block erase only occurs when v pp = v pph1 or v pph2 . if the erase operation is attempted at v pp v pph1 or v pph2 , erratic results may occur. 4.6. program command program command operates on one byte at a time. this command specifies the address and data to be programmed. after the cui receives the command, the wsm takes over, controlling the program and verify algorithms internally. after the program command is written, the device automatically outputs the status register data when read. when programming is complete, the status register may be checked. if a program error is detected, the status register should be cleared before corrective action is taken by the software. the internal wsm verification error checking only detects 1s that does not successfully program to 0s. the cui remains in read status register mode until it receives another command. reliable programming only occurs when v pp = v pph1 or v pph2 . if programming is attempted at v pp v pph1 or v pph2 , erratic results may occur. successful program operation also requires that the corresponding block?s write-lock bit be cleared and that the corresponding write-protect pin (tbl# or wp#) be inactive. if program operation is attempted when the block is locked, the operation will fail.
intel ? 82802ab/ac firmware hub r datasheet 23 4.7. block erase suspend command the block erase suspend command allows block-erase interruption to read or program data in another block of memory. once the block erase process starts, writing the block erase suspend command requests that the wsm suspend the block erase sequence at a predetermined point in the algorithm. the device outputs status register data when read after the block erase suspend command is written. polling the status register can help determine when the block erase operation was suspended. after a successful suspend, a read array command may be written to read data from a block other than the suspended block. a program command sequence may also be issued during erase suspend to program data in blocks other that the block currently in the erase suspend mode. the other valid commands while block erase is suspended include read status register and block erase resume. after a block erase resume command is written, the wsm will continue the block erase process. v pp must remain at v pph1/2 (the same v pp level initially used for the block erase) while block erase is suspended. rst# or init# must also remain at v ih . block erase cannot resume until program operations initiated during block erase suspend have completed. 4.8. program suspend comand the program suspend command allows program interruption to read data in other memory locations. once the program process starts, writing the program suspend command requests that the wsm suspend the program sequence at a predetermined point in the algorithm. the device continues to output status register data when read after the program suspend command is written. polling status register bits will help determine when the program operation was suspended. after a successful suspend, a read array command can be written to read data from locations other than that which is suspended. the only other valid commands while program is suspended are read status register and program resume. after program resume command is written, the wsm will continue the programming process. v pp must remain at v pph1/2 (the same v pp level used for program) while in program suspend mode. rst# or init# must also remain at v ih . 4.9. register based locking, general-purpose input, and random number generator registers a series of registers are available in the intel fwh to provide software read- and write-locking and gpi feedback. also available are the set of control registers for controlling and gathering random numbers. these registers are accessible through standard addressable memory space (see the following table). it is recommended that the gpi pins be in the desired state before fwh4 is brought low for the beginning of the next bus cycle, and remain in that state until the end of the read.
intel ? 82802ab/ac firmware hub r 24 datasheet table 5. intel firmware hub register configuration map memory address mnemonic register name default type ffbf0002h t_block_lk top block lock register (4-8-mbit fwh) 01h r/w ffbe0002h t_minus01_lk top block [-1] lock register (4-8-mbit fwh) 01h r/w ffbd0002h t_minus02_lk top block [-2] lock register (4-8-mbit fwh) 01h r/w ffbc0002h t_minus03_lk top block [-3] lock register (4-8-mbit fwh) 01h r/w ffbb0002h t_minus04_lk top block [-4] lock register (4-8-mbit fwh) 01h r/w ffba0002h t_minus05_lk top block [-5] lock register (4-8-mbit fwh) 01h r/w ffb90002h t_minus06_lk top block [-6] lock register (4-8-mbit fwh) 01h r/w ffb80002h t_minus07_lk top block [-7] lock register (4-8-mbit fwh) 01h r/w ffb70002h t_minus08_lk top block [-8] lock register (8-mbit fwh) 01h r/w ffb60002h t_minus09_lk top block [-9] lock register (8-mbit fwh) 01h r/w ffb50002h t_minus10_lk top block [-10] lock register (8-mbit fwh) 01h r/w ffb40002h t_minus11_lk top block [-11] lock register (8-mbit fwh) 01h r/w ffb30002h t_minus12_lk top block [-12] lock register (8-mbit fwh) 01h r/w ffb20002h t_minus13_lk top block [-13] lock register (8-mbit fwh) 01h r/w ffb10002h t_minus14_lk top block [-14] lock register (8-mbit fwh) 01h r/w ffb00002h t_minus15_lk top block [-15] lock register (8-mbit fwh) 01h r/w ffbc0100h fgpi_reg fwh general-purpose input register n/a ro ffbc015fh rng hardware status register 40h* r/w ffbc0160h rng data status register 0 ro ffbc0161h rng data register n/a ro * assumes rng is present and not disabled.
intel ? 82802ab/ac firmware hub r datasheet 25 4.9.1. t_block_lk and t_minusxx_lk ? block-locking registers memory address: ffbx0002h (x = f-0h) default value: 01h access: r/w size: 8 bits (each) bit function 7:3 reserved 2 read-lock 1 = prevents read operations in the block where set. 0 = normal operation for reads in the block where clear. this is the default state. 1 lock-down 1 = prevents further set or clear operations to the write lock and read lock bits. lock-down only can be set, but not cleared. the block will remain locked-down until reset (with rst# or init#), or until the device is power-cycled. 0 = normal operation for write lock and read lock bit altering in the block where clear. this is the default state. 0 write-lock 1 = prevents program or erase operations in the block where set. this is the default state. 0 = normal operation for programming and erase in the block where clear. table 6. register-based locking value definitions data reserved data 7:3 read lock, data 2 lock-down, data 1 write lock, data 0 resulting block state (1) . 00h 00000 0 0 0 full access 01h 00000 0 0 1 write locked. default state at power- up 02h 00000 0 1 0 locked open (full access locked down). 03h 00000 0 1 1 write-locked down. 04h 00000 1 0 0 read locked. 05h 00000 1 0 1 read and write locked. 06h 00000 1 1 0 read-locked down. 07h 00000 1 1 1 read- and write-locked down. note: the write-lock bit must be set to the desired protection state prior to starting a program or erase operation, since it is sampled at the beginning of the operation. changing the state of the write-lock bit during a program or erase operation may cause unpredictable results. if the state of the write-lock bit changes during a program suspend or erase suspend state, changes in the block?s locking status do not occur immediately. the suspended operation may be resumed successfully. the new lock status will take place after the program or erase operation completes. the individual bit functions are described in the following sections.
intel ? 82802ab/ac firmware hub r 26 datasheet write lock the default write status of all blocks upon power-up is write-locked. any program or erase operations attempted on a locked block will return an error in the status register (indicating block lock). the status of the locked block can be changed to unlocked by clearing the write-lock bit, provided the lock-down bit also is not set. the current write-lock status of a particular block can be determined by reading the corresponding write-lock bit. the write-lock functions in conjunction with the hardware write-lock pins, tbl# and wp#. when active, these pins take precedence over the register locking function and write- lock the top block or remaining blocks, respectively. reading this register will not read the state of the tbl# or wp# pin. read lock the default read status of all blocks upon power-up is read-unlocked. when a block?s read-lock bit is set, data cannot be read from that block. an attempted read from a read-locked block will result in the data 00h. (note that failure is not reflected in the status register.) the read-lock status can be unlocked by clearing the read-lock bit, provided the lock-down bit has not been set. the current read-lock status of a particular block can be determined by reading the corresponding read-lock bit. lock-down in the intel fwh interface mode, the default lock-down status of all blocks upon power-up is not-locked- down. the lock-down bit for any block may be set, but only once, because future attempts to change that block-locking register will be ignored. the lock-down bit is cleared only upon a device reset with rst# or init#. the current lock-down status of a particular block can be determined by reading the corresponding lock-down bit. once a block?s lock-down bit is set, the read- and write-lock bits for that block can no longer be modified, and the block is locked-down in its current state of read and write accessibility. 4.9.2. general-purpose input register this register reads the status of the fgpi [4:0] pins on the intel fwh. since this is a pass-through register, there is no default value, only the state of the pins at power-up. 4.9.2.1. gpi_reg ? general-purpose input register memory address: ffbc0100h default value: n/a access: r0 size: 8 bits bit function 7:5 reserved 4 fgpi[4]. reads status of general-purpose input pin (plcc-30/tsop-7). 3 fgpi[3]. reads status of general-purpose input pin (plcc-3/tsop-15). 2 fgpi[2]. reads status of general-purpose input pin (plcc-4/tsop-16). 1 fgpi[1]. reads status of general-purpose input pin (plcc-5/tsop-17). 0 fgpi[0]. reads status of general-purpose input pin (plcc-6/tsop-18).
intel ? 82802ab/ac firmware hub r datasheet 27 4.9.3. random number generator registers when enabled and active, the random number generator (rng) is designed to fill an 8-bit register, a bit at a time, with hardware-generated random numbers. when this register is full, a flag bit in the rng data status register transitions to a 1, indicating that a valid random number is ready to be read. this bit will immediately reset to 0 upon reading the rng data register. the advantages of random numbers over pseudo-random numbers as well as a brief overview of the simple mathematics of testing rngs are discussed superficially in the companion document, the intel ? platform rng tech brief , which is available online. 4.9.3.1. rng hardware status register memory address: ffbc015fh default value: 40h, for typical component out of reset access: ro size: 8 bits bit function 7 reserved 6 rng present?ro. determines whether or not an rng is present on this component, or if it has been disabled. 1 = rng present 0 = rng not present 5:1 reserved 0 rng enabled?r/w. determines whether the rng is generating a random number. 1 = rng enabled 0 = rng disabled 4.9.3.2. rng data status register memory address: ffbc0160h default value: 00h access: ro size: 8 bits bit function 7:1 reserved 0 rng output valid. determines whether the rng data register contains a valid random number. 1 = rng data register contians valid random data 0 = rng data register contents not valid
intel ? 82802ab/ac firmware hub r 28 datasheet 4.9.3.3. rng data register memory address: ffbc0161h default value: 40h, for typical component out of reset access: ro size: 8 bits bit function 7:0 rng output : (should only be used if rng data status register indicates valid output.) 4.10. using the random number generator the intel firmware hub integrates a random number generator that utilizes thermal noise generated as a result of the inherently random quantum mechanical properties of silicon, in order to modulate a proven hardware rng design. internal circuitry is included to enhance the entropy of the output. since the output of the rng is non-deterministic, it is an excellent choice for cryptography applications, but it also is a convenient source of random numbers for mathematics, modeling, graphics algorithms, artificial intelligence, entertainment, and many other applications. the fact that it is a component of the platform and may be utilized remotely on a locked-away server makes it an ideal (and much more reliable) source of entropy for applications that, in the past, have relied exclusively on a key press or other environmental input. several intel firmware hub components may be used in tandem (see the following section) when additional rng bandwidth is required. when not generating new random bits, the rng circuitry will enter a low power state. 4.11. detecting and initializing the rng device before any process attempts to read random data directly from the intel firmware hub rng device, it should execute a process to verify that a supported rng device is available for use, enable the device, and verify the correct functionality. this initialization process is described in a following subsection. 4.11.1. detecting the rng device the manufacturer code and hardware status registers are used to determine whether a supported rng device is available on the system. step 1: from the system bios or using the read identifier codes command, as specified in the intel ? 82802ab/82802ac firmware hub (fwh) datasheet, verify the intel ? 82802 manufacturer code. step 2: if a valid intel ? 82802 fwh is found, then the rng present bit (bit 6) of the hardware status register should be checked in order to verify that an rng device is available. note: there is a chance that, even if no rng device is present, the physical memory locations described above may coincidentally match the values expected for an rng device. for this reason, before random data is sent to an application, the device should be exercised to verify that it is indeed an rng. this can be accomplished by enabling the device and running an initial test (e.g., fips (federal information processing standard) 140-1) before use.
intel ? 82802ab/ac firmware hub r datasheet 29 4.11.2. initializing the rng device once the rng device is detected, it must be enabled and should be tested before use. step 1: the rng enabled bit (bit 0) of the hardware status register must be set to enable the rng device. step 2: once the rng is enabled, an initial read of the rng data register should be made to clear any preexisting data from the register. step 3: a test (e.g., fips 140-1) should be run on the rng device. this test will ensure that there was no error in detecting the device and that the device is functioning properly. 4.11.3. selecting appropriate fwh ids and densities it is possible, using different id strapping, to use multiple fwh components in a system. while the fwh protocol supports up to 16 fwh devices, the bios support, bus loading or the attaching bridge may limit this number. note that, regardless of the number of fwh components, the maximum ?window? of the fwh array visible at one time is 4 mb (for intel ? ich1) and 8mb for intel ? ich2. the boot device must have an id (as determined by id [0:3]) of 0. for clarity, it is advisable that subsequent devices use incremental numbering. the most straightforward method of using multiple fwh components is to use devices of equal density. this is the recommended technique. in special applications, when it is desirable to use multiple fwh components of different densities?if multiple rngs or more gpis are required, for instance, without the need for greater array space?ids must be chosen such that component memory array spaces do not cross the boundaries delimited by the highest-capacity device, as illustrated in the following table. for example, in a design with 8- and 4-mbit components, the 8-mbit part must either be first or must be after enough 4-mbit parts to add up to a multiple of 8 mbits. yes no yes 8 mbits 4 mbits 4 mbits 8 mbits 4 mbits 4 mbits 8 mbits biggest is 8 mbits.
intel ? 82802ab/ac firmware hub r 30 datasheet 4.11.4. mapping fwh devices onto memory map there is 4 mb of available memory space devoted to the fwh. therefore, the intel ich has the ability to select which fwh device maps into each region of the system address space. in the existing intel ich, the address map is broken up into eight 512-kb segments. the bios select register in the intel ich is a 32-bit register that contains the needed mapping information, thereby determining which fwh receives requests from which portion of the address map. for example, in a system with four 8-mbit devices, this register would be 00112233h, which is the default power-up state for this register. in a system with eight 4-mbit devices, the register must be changed to 01234567h. note: the fwh indicated in the most-significant nibble of the register may be shadowed elsewhere in the system memory map. the fwh with id 0 may not be re-mapped. 4.11.5. paging fwh devices for greater than 4 mb of fwh memory in certain applications, even a 4-mb window of flash memory is inadequate. it is possible to exceed this amount by using a paging scheme. individual fwh devices may then be ?swapped? in and out of system memory space. this must be implemented at the bios level, to permit modification of the intel ich bios select register. a number of paging algorithms may be used successfully with the fwh memory space, using the intel ich bios select register. this register, then, determines which fwh device gets mapped into each 512 kb ?slice? of the system memory map. the 0th fwh (id=0) may not be remapped. reference the intel ? 82801aa (ich) and intel ? 82801ab (ich0) i/o controller hub datasheet (order number: 290655) for information regarding these components and the bios select register. note: the paging of fwh devices will also ?page? features, potentially affecting the visibility or location of the fgpi register (see section 4.9.2.1) or of an active/ready rng. when a paging scheme is used, it is recommended that critical fpgis be used only on the id 0 fwh device, which must remain mapped at the top of memory. ideally, the rng driver in a system with more than four fwhs should verify the mapping of fwhs in order to keep track of which rngs are active and which are present in the memory map. there is no convenient way, aside from checking the select register, to determine which ided fwh is in which location in the memory map. 4.11.6. programming multiple fwh devices special considerations must be taken into account when programming multiple fwh devices in-system. since there is no id support in the a/a mux mode, the recommended means of programming multiple devices is either out-of-system programming with standalone prom programmers or in-system programming using the fwh mode. in cases where programming time is critical or ate programming is required, provisions should be made to isolate the component from its neighboring devices during a/a mux programming, or the other devices should be held in a reset (or otherwise disabled) state until programming of the intended device is complete. do not switch one component into the a/a mux mode, thereby leaving the others in the fwh mode.
intel ? 82802ab/ac firmware hub r datasheet 31 4.12. cui automation flowcharts figure 6. automated block erase flowchart sr.7 = 0 1 start write 20h, block address write d0h, block address full status check if desired block erase complete full status check procedure 1 read status register data (see above) 1 0 read status register 1 0 command sequence error sr.3 = sr.5 = sr.4,5 = block erase error bus operation command comments standby check sr.4,5 both 1 = command sequence error standby sr.5, sr.4, and sr.3 are only cleared by the clear status register command in cases where multiple blocks are erased before full status is checked. if error is detected, clear the status register before attempting retry or other error recovery. check sr.5 1 = block erase error standby bus operation command comments write write erase setup read data = 20h addr = within block to be erased check sr.7 1 = wsm ready 0 = wsm busy repeat for subsequent block erasures. full status check can be done after each block erase, or after a sequence of block erasures. write ffh after the last operation to place device in read array mode. status register data standby erase confirm data = d0h addr = within block to be erased block erase successful check sr.3 1 = v error detect pp v range error pp
intel ? 82802ab/ac firmware hub r 32 datasheet this page left intentionally blank
intel ? 82802ab/ac firmware hub r datasheet 33 5. electrical specifications 5.1. absolute maximum ratings case temperature under bias:......................... ?10 c to +85 c storage temperature: ................................... ?65 c to +125 c supply voltage with respect to vss ..................-0.2 v to 4.1 v voltage on any pin (except v pp ):?0.5 v to +vcc + 0.5 v (1,2,5) v pp voltage: ........................................... ?0.5 v to +14.0 v (1,2,4) output short-circuit current: ...................................... 100 ma (3) *warning: stressing the device beyond the ?absolute maximum r atings? may cause permanent damage. these are stress ratings only. operation beyond the ?operating conditions? is not recommended and extended exposure beyond the ?operating conditions? may affect device reliability. note: 1. all specified voltages are with respect to gnd. the minimum dc voltage on the v pp pin is ?0.5 v. during transitions, this level may undershoot to ?2.0 v for periods of <20 ns. during transitions, this level may overshoot to v cc + 2.0 v for periods of <20 ns. 2. the maximum dc voltage on v pp may overshoot to +14.0 v for periods of <20 ns. 3. output shorted for no more than one second. no more than one output is shorted at a time. this note applies only to non-pci outputs. 4. connection to supply of v hh is allowed for a maximum cumulative period of 80 hours. 5. do not violate processor or chipset limitations on the init# pin. 5.2. operating conditions table 7. temperature and vcc symbol parameter notes min. max. unit test condition t c operating temperature 1 0 +85 c case temperature v cc v cc supply voltage (3.3 v 0.3 v) 3.0 3.6 v note: 1. this temperature requirement differs from the normal commercial operating condition of flash memories.
intel ? 82802ab/ac firmware hub r 34 datasheet 5.2.1. interface dc input/output specifications table 8. intel fwh interface dc input/output specifications symbol parameter conditions min. max. units notes v ih input high voltage 0.5 v cc v cc +0.5 v 3 v ih (init#) init# input high voltage 1.35 v cc +0.5 v 5 v il input low voltage -0.5 0.3 v cc v 3 i il input leakage current 0 < v in < v cc 10 a 1,4 v oh output high voltage iout = -500 a 0.9 v cc v v ol output low voltage iout = 1500 a 0.1 v cc v c in input pin capacitance 13 pf c clk clk pin capacitance 3 12 pf l pin recommended pin inductance 20 nh 2 note: 1. input leakage currents include hi-z output leakage for all bi-directional buffers with tri-state outputs. 2. refer to pci spec. 3. inputs are not ?5 volt safe.? 4. i il may be changed on ic and id pins (up to 200 a), if pulled against internal pull-downs. refer to the pin descriptions (table 1). 5. do not violate processor or chipset specifications regarding the init# pin voltage.
intel ? 82802ab/ac firmware hub r datasheet 35 table 9. power supply specifications ? all interfaces symbol parameter conditions min. max. units notes vpph1 vpp voltage 3.0 3.6 v vpph2 vpp voltage 11.4 12.6 v vpplk vpp lockout voltage 1.5 v vlko vcc lockout voltage 1.5 v iccsl1 vcc stand-by current (fwh interface) voltage range of all inputs is vih to vil, fwh4 = vih, vcc = 3.6 v, clk f = 33 mhz no internal operations in progress. 100 a 2,3,4 iccsl2 vcc stand-by current (fwh interface) fwh4 = vil vcc = 3.6 v, clk f = 33 mhz no internal operations in progress. 10 ma 2,3,4 icca vcc active current vcc = vcc max, clk f = 33 mhz any internal operation in progress, iout = 0ma 67 ma 2,3,5 i ppr v pp read current v pp v cc 200 a 2 i ppwe v pp program or v pp = 3.0-3.6 v 40 ma 2 erase current v pp = 11.4-12.6 v 15 ma 2 note: 1. all currents are rms, unless otherwise noted. these currents are valid for all packages. 2. v pp = v cc 3. v ih = 0.9 v cc , v il = 0.1 v cc per the pci output v oh and v ol specifications of table 8. 4. this number is the worst case of i pp + i cc memory core + i cc fwh interface.
intel ? 82802ab/ac firmware hub r 36 datasheet 5.2.2. interface ac input/output specifications table 10. intel fwh interface ac input/output specifications symbol parameter condition min. max. units notes ioh(ac) switching current high 0 < v out 0.3 v cc -12 v cc ma 0.3 v cc < v out < 0.9 v cc -17.1 (v cc -v out ) ma 0.7 v cc < v out < v cc equation c (test point) v out = 0.7 v cc -32 v cc ma iol(ac) switching current low v cc > v out 0.6 v cc 16 v cc ma 0.6 v cc > v out > 0.1 v cc -17.1 (v cc -v out ) ma 0.18 v cc > v out > 0 equation d (test point) v out = 0.18 v cc 38 v cc ma icl low clamp current -3 < v in -1 -25 + (v in +1) / 0.015 ma ich high clamp current v cc +4 > v in v cc +1 25 + (v in -v cc -1) / 0.015 ma slewr output rise slew rate 0.2 v cc - 0.6 v cc load 1 4 v/ns 1 slewf output fall slew rate 0.6 v cc - 0.2 v cc load 1 4 v/ns 1 note: 1. pci specification output load is used.
intel ? 82802ab/ac firmware hub r datasheet 37 5.2.3. intel fwh interface ac timing specifications 5.2.3.1. clock specification table 11. clock specification symbol parameter condition min. max. units notes tcyc clk cycle time 30 ns 1 thigh clk high time 11 ns tlow clk low time 11 ns - clk slew rate peak-to-peak 1 4 v/ns - rst# or init# slew rate 50 mv/ns 2 note: 1. pci components must work with any clock frequency between nominal dc and 33 mhz. frequencies less than 16 mhz may be guaranteed by design rather than testing. refer to the pci specificaiton. 2. applies only to the rising edge of the signal. see chapter 4 of the pci electrical specification. figure 7. clock waveform 0.3 vc c 0.4 vc c 0.5 vcc 0.2 vc c 0.6 vcc t_cy c t_high t_lo w 0.4 vcc, p-to-p (minimum)
intel ? 82802ab/ac firmware hub r 38 datasheet 5.2.3.2. signal timing parameters table 12. signal timing parameters symbol pci symbol parameter condition min. max. units notes tchqv t val clk to data out 2 11 ns 1 tchqx t on clk to active (float to active delay) 2 ns 2 tchqz t off clk to inactive (active to float delay) 28 ns 2 tavch tdvch t su input setup time 7 ns 3 tchax tchdx t h input hold time 0 ns 3 tvspl t rst reset active time after power stable 1 ms tcspl t rst-clk reset active time after clk stable 100 s tplqz t rst-off reset active to output float delay 48 ns 2 note: 1. minimum and maximum times have different loads. see pci spec. 2. for purposes of active/float timing measurements, the hi-z or off state is defined as that in which the total current delivered through the component pin is less than or equal to the leakage current specification. 3. this parameter applies to any input type (excluding clk). figure 8. output timing parameters t_off t_val v_test t_on v_th v_tl clk fwh[3:0] (valid output data) fwh[3:0] (float output data)
intel ? 82802ab/ac firmware hub r datasheet 39 figure 9. input timing parameters t_su v_test v_th v_tl clk fwh[3:0] (valid input data) t_h inputs valid v_max table 13. interface measurement condition parameters symbol value units notes v th 0.6 v cc v 1 v tl 0.2 v cc 1 v test 0.4 v cc v max 0.4 v cc 1 input signal edge rate 1 v/ns note: 1. the input test environment uses 0.1 v cc of overdrive over v ih and v il . timing parameters must be met with no more overdrive than this. vmax specifies the maximum peak-to-peak waveform allowed for measuring the input timing. production testing may use different voltage values, but must correlate results back to these parameters. reset operations ih v il v rst# (p) p1 table 14. ac waveform for reset operation # symbol parameter min. max. unit notes p1 (1) t plph rst# or init# pulse low time (if rst# or init# is tied to v cc , this specification is not applicable.) 100 ns 1 note: 1. there will be a 20- s reset latency if a reset procedure is performed during a programming or erase operation.
intel ? 82802ab/ac firmware hub r 40 datasheet 5.3. block programming times table 15. programming times 3.3 v v pp 12 v v pp parameter notes typ. (1) max. typ. (1) max. unit byte program time 2 17 300 7.0 125 s block program time 2 1.1 4.0 0.5 1.5 sec block erase time 2 0.8 6.0 0.3 4.0 sec note: 1. typical values measured at t a = +25c and nominal voltages. 2. excludes system-level overhead. 5.4. intel firmware hub interface the firmware hub relies on the intel firmware hub interface to communicate with the outside world. this interface consists of four bi-directional signals and one ?control? input. the timing and electrical parameters of the fwh interface are similar to those of the lpc interface, to provide compatibility between the interfaces, but differ in cases mentioned earlier in this section (clock pin capacitance), as well as in certain timing parameters. the intel ich has been engineered to accommodate both interfaces, which allows the intel fwh interface signals to be communicated over the same set of pins as lpc. the intel fwh interface is designed to use an lpc-compatible start cycle, with a reserved cycle type code. this ensures that all lpc devices present on the shared interface will ignore cycles destined for the fwh, without becoming ?confused? by the different protocol. this section contains timing and protocol information for the intel fwh interface. note that the intel fwh interface is a licensed interface, so the appropriate license must be obtained from intel for components supporting the intel fwh interface (e.g., asics, plds). 5.4.1. intel fwh interface cycles when the intel fwh interface is active, information is transferred to and from the fwh by a series of ?fields,? where each field contains 4 bits of data. many fields are one clock cycle in length but can be of variable length, depending upon the nature of the field. field sequences and contents are strictly defined for read and write operations. the following tables list the field sequences for read and write cycles. addresses in this section refer to addresses as seen from the fwh?s ?point of view,? so some calculation will be required to translate these to the actual locations in the memory map (and vice versa). 5.4.1.1. read cycle sequence the firmware hub supports single-byte or multibyte reads. the logic waveforms for these cycles are shown in table 16 and figure 11
intel ? 82802ab/ac firmware hub r datasheet 41 table 16. fwh read cycle clock cycle field name field contents 1 fwh[3:0] fwh[3:0] direction comments 1 start 1101 in fwh4 must be active (low) for the part to respond. only the last start field (before fwh4 transitioning high) should be recognized. the start field contents indicate an fwh memory read cycle. 2 idsel 0000 to 1111 in indicates which fwh device should respond. if the idsel (id select) field matches the value id[3:0], then that particular device will respond to subsequent commands. 3-9 imaddr yyyy in these seven clock cycles make up the 28-bit memory address. yyyy is one nibble of the entire address. addresses are transferred most-significant nibble first. on multibyte data transfers, lower-order addresses will be zero, depending on page size. 10 imsize 0000 (1 byte) in a field of this size indicates how many bytes will be transferred during multibyte operations. the fwh will only support single-byte transfers. 11 tar0 1111 in then float in this clock cycle, the master (intel ich) has driven the bus to all 1s and then floats the bus, prior to the next clock cycle. this is the first part of the bus ?turnaround cycle.? 12 tar1 1111 (float) float then out the fwh takes control of the bus during this cycle. during the next clock cycle, it will be driving ?sync data.? 13-14 wsync 0101 (wait) out the fwh outputs the value 0101, a wait-sync (wsync, a.k.a. ?short-sync?), for two clock cycles. this value indicates to the master (intel ich) that data is not yet available from the part. this number of wait-syncs is a function of the device?s access time. 15 rsync 0000 (ready) out during this clock cycle, the fwh will generate a ?ready- sync? (rsync) indicating that the least-significant nibble of the least-significant byte will be available during the next clock cycle. 16 data yyyy out yyyy is the least-significant nibble of the least- significant data byte. 17 data yyyy out yyyy is the most-significant nibble of the least- significant data byte. 17+ 3 x 2 n-1 + 2 n ?data? 2 wsyncs + 1 rsync + 2 data out n = imsize. each subsequent byte of data requires 2 wait-syncs + 1 ready-sync + 2 data nibbles. the fwh supports only n=0000 (single-byte) reads. previous + 1 tar0 1111 out then float in this clock cycle, the inel fwh has driven the bus to all ones and then floats the bus prior to the next clock cycle. this is the first part of the bus ?turnaround cycle.? previous + 1 tar1 1111 (float) float then in the master (intel ich) resumes control of the bus during this cycle. note: 1. field contents are valid on the rising edge of the present clock cycle.
intel ? 82802ab/ac firmware hub r 42 datasheet 5.4.1.2. single-byte read waveforms figure 10. fwh single-byte read waveforms imaddr str clk fwh[3:0] fwh4 ids ims tar sync(3) data tar 5.4.1.3. write cycle sequence the firmware hub only supports single-byte writes. each byte represents either the data to be written or a valid flash command. refer to the waveforms in figure 11. table 17. fwh write cycle clock cycle field name field contents 1 fwh[3:0] fwh[3:0] direction comments 1 start 1110 in fwh4 must be active (low) for the part to respond. only the last start field (before fwh4 transitioning high) should be recognized. the start field contents indicate an fwh memory write cycle. 2 idsel 0000 to 1111 in indicates which fwh device should respond. if the idsel (id select) field matches the value id[3:0], then that particular device will respond to subsequent commands. 3-9 imaddr yyyy in these seven clock cycles make up the 28-bit memory address. yyyy is one nibble of the entire address. addresses are transferred most-significant nibble first. 10 imsize 0000 (1 byte) in this size field indicates how many bytes will be transferred during read/write operations. the fwh only supports single-byte writes. 11 data yyyy in this field is the least-significant nibble of the data byte. this data is either the data to be programmed into the flash memory or any valid flash command. 12 data yyyy in this field is the most-significant nibble of the data byte. 13 tar0 1111 in then float in this clock cycle, the master (intel ich) has driven the bus to all 1s and then floats the bus prior to the next clock cycle. this is the first part of the bus ?turnaround cycle.? 14 tar1 1111 (float) float then out the fwh takes control of the bus during this cycle. during the next clock cycle it will be driving the ?sync? data. 15 rsync 0000 out the fwh outputs the values 0000, indicating that it has received data or a flash command.
intel ? 82802ab/ac firmware hub r datasheet 43 clock cycle field name field contents 1 fwh[3:0] fwh[3:0] direction comments 16 tar0 1111 out then float in this clock cycle, the fwh has driven the bus to all 1s and then floats the bus prior to the next clock cycle. this is the first part of the bus ?turnaround cycle.? 17 tar1 1111 (float) float then in the master (intel ich) resumes control of the bus during this cycle. note: 1. field contents are valid on the rising edge of the present clock cycle. 5.4.1.4. write waveforms figure 11. write waveforms imaddr str clk fwh[3:0] fwh4 ids ims tar syn c data tar 5.4.1.5. response to invalid fields during fwh operations, the intel fwh will not explicitly indicate that it has received invalid field sequences. the response to specific invalid fields or sequences is as follows: ? address out of range: the intel fwh address sequence is 7 fields long (28 bits), but only the last five address fields (20 bits) will be decoded by an 8-mbit fwh. (for a 4-mbit density, the most- significant bit (fwh3) in the third address field also will be ignored.) the intel fwh will respond to these lower addresses, regardless of the value of the more-significant address bits. address a22 has the special function of directing reads and writes to the flash core (a22 = 1) or to the register space (a22 = 0). ? invalid imsize field: if the intel fwh receives an invalid size field during a read or write operation, the internal state machine will reset and no operation will be attempted. the intel fwh will generate no response of any kind in this situation. invalid-size fields for a read cycle are anything but 0000. invalid-size fields for a write cycle are anything but 0000. when accessing register space, invalid field sizes are anything but 0000. ? non-page-aligned address: the intel fwh assumes that multibyte read addresses are page aligned (i.e., for a 32-byte access, the lower 5 address bits will be zero). if they are not zero, the first byte of data returned by the intel fwh will correspond to that explicit address, and subsequent data will be as if the first address was indeed page aligned. once valid start, idsel, and imsize fields are received, the intel fwh always will respond to subsequent inputs as if they were valid. as long as the states of fwh [3:0] and fwh4 are known, the response of the intel fwh to signals received during the fwh cycle should be predictable. the intel fwh will make no attempt to check the validity of incoming flash operation commands.
intel ? 82802ab/ac firmware hub r 44 datasheet 5.4.1.6. abort operations fwh4 active (low) indicates either that a start cycle will eventually occur or that an abort is in progress. in either case, if fwh4 is asserted, the intel fwh will ?immediately? tri-state its outputs and the fwh state machine will reset. during a write cycle, there is a possibility that an internal flash write or erase operation is in progress (or has just been initiated). if fwh4 is asserted during this time frame, the internal operation will not abort. the software must send an explicit flash command to terminate or suspend the operation. the internal fwh state machine will not initiate a flash write or erase operation until it has received the last data nibble from the chipset. this means that fwh4 can be asserted as late as this cycle (?cycle 12?) and no internal flash operation will be attempted. however, since the intel fwh will start ?processing? incoming data before it generates its sync field, it should be considered a non-buffered peripheral device. 5.4.1.7. intel fwh cycle timing information refer to figure figure 12 and figure 13. table 18. signal timing parameters symbol ?pci symbol? parameter condition min. max. units notes tchqv t val clk to data out 2 11 ns 1 tchqx t on clk to active (float to active delay) 2 ns 2 tchqz t off clk to inactive (active to float delay) 28 ns 2 tavch tdvch t su input setup time 7 ns 3 tchax tchdx t h input hold time 0 ns 3 tvspl t rst reset active time after power stable 1 ms tcspl t rst-clk reset active time after clk stable 100 s tplqz t rst-off reset active to output float delay 48 ns 2 note: 1. minimum and maximum times have different loads. see the pci specification. 2. for purposes of active/float timing measurements, the hi-z or ?off? state is defined as the state where the total current delivered through the component pin is less than or equal to the leakage current specification. 3. this parameter applies to any input type (excluding clk).
intel ? 82802ab/ac firmware hub r datasheet 45 5.5. rng parameters table 19. rng timing characteristics # sym parameter notes typ. max. unit write re = 1 to dword ready or read dword to new dword ready 1 450 1500 s average sustained throughput 1 13 50 s/bit note: 1. sampled, not 100% tested. table 20. rng statistical characteristics # sym parameter notes min. typ. max. unit b2 fractional probability of excess 1s 1,2,3 316 10-6 ac auto correlation coefficient 3 632 10-6 fom figure of merit 3 7.5 17 note: 1. sampled, not 100% tested. figure 12. intel fwh output timing parameters t_off t_val v_test t_on v_th v_tl clk fwh[3:0] (valid output data) fwh[3:0] (float output data)
intel ? 82802ab/ac firmware hub r 46 datasheet figure 13. intel fwh input timing parameters t_su v_test v_th v_tl clk fwh[3:0] (valid input data) t_h inputs valid v_max
intel ? 82802ab/ac firmware hub r datasheet 47 6. prom programming specifications 6.1. programming (?a/a mux?) mode operation the intel ? 82802 is designed to offer a parallel programming mode for faster factory programming. this mode, called the a/a mux mode, is selected by ic high. the ic pin is pulled down internally in the intel ? 82802, so it should be expected that a modest current will be drawn. (see the pin descriptions in table 1 for further information.) the following information applies only to the intel ? 82802 when in the a/a mux mode. information regarding the fwh mode (i.e., the standard operating mode) is provided in earlier chapters of this document 6.2. bus operation all a/a mux bus cycles can be conformed to operate on most automated test equipment and prom programmers. 6.2.1. output disable/enable with oe# at the logic-high level (v ih ), the device outputs are disabled. output pins dq0?dq7 are placed in the high-impedance state. with oe# at the logic-low level (v il ), the device outputs are enabled. output pins dq0?dq7 are placed in the output-drive state. 6.2.2. row/column addresses r/c# is the a/a mux control pin used to latch row (a0?a10) and column addresses (a11?a18/4 mbits, or a[11:19] /8 mbits). r/c# latches row addresses on the falling edge and column addresses on the rising edge. 6.2.3. read operation block information, identifier codes or status register data can be read independently of the v pp voltage. the first task is to write the appropriate read-mode command (read array, read identifier codes or read status register) to the cui. upon initial device power-up or after exit from reset, the device defaults to the read array mode. four control pins dictate the data flow into and out of the component: r/c#, oe#, we#, and rst#. r/c# is the a/a mux control pin used to latch row and column addresses. oe#, the data output control pin (dq0?dq7), drives the selected memory data onto the i/o bus, when active. we# and rst# must be at v ih .
intel ? 82802ab/ac firmware hub r 48 datasheet 6.2.4. read identifier codes operation the read identifier codes operation outputs the manufacturer and device codes (see table 4). using the manufacturer and device codes, automated test equipment (ate) or prom programmer software can confirm the proper device id. 6.2.5. write operation the cui does not occupy a specific addressable memory location. it is written to when we# is active and oe# = v ih . the address previously captured by r/c# transitions and the data needed to execute a command are latched on the we# rising edge. table 21. bus operations mode notes rst# oe# we# address v pp dq[0:7] read 1,2,6 v ih v il v ih x x d out output disable 6 v ih v ih v ih x x high z read identifier codes 3,6 v ih v il v ih note 3 x note 3 write 4,5,6 v ih v ih v il x x d in note: 1. when v pp v pplk , the memory contents can be read, but not altered. 2. x can be v il or v ih for the control and address input pins and v pplk or v pph1 /2 for the v pp supply pin. see the dc characteristics for the v pplk and v pph1 /2 voltages. 3. see table 4 for the read identifier code data and addresses. 4. command writes involving block erase or program are reliably executed when v pp = v pph1 /2 and v cc = v cc 0.3 v. 5. refer to table 2 for the valid d in during a write operation. 6. v ih and v il refer to the dc characteristics associated flash memory output buffers: v il min = -0.5v, v il max = 0.8v and v ih min = 2.0v, v ih max = v cc + 0.5v. 6.3. command definitions flash core programming commands in a/a mux mode are identical to commands for the fwh mode. refer to section 4 of this document. 6.4. electrical characteristics in a/a mux mode certain specifications differ from the previous sections, when programming in the a/a mux mode. the following subsections provide this data. any information not provided here is not specific to the a/a mux mode. refer to section 5 of this document and use the intel fwh mode specifications.
intel ? 82802ab/ac firmware hub r datasheet 49 6.4.1. reset operations # symbol parameter notes min. max. unit p1 t plph rst# pulse low time (if rst# is tied to v cc , this specification is not applicable.) 100 ns p2 t plrh rst# low to reset during block erase or program 1, 2 20 s note: 1. if rst# is asserted when the wsm is not busy (ry/by# = ?1?), the reset will complete within 100 ns. 2. a reset time, t phav , is required from the latter of ry/by# or rst# going high until outputs are valid. 6.4.2. ac waveforms for reset operations ih v il v rst# (p) ih v il v ry/by# ( r ) p1 p2 6.4.3. a/a mux read-only operations (1,3) # symbol parameter notes min. max. unit r1 t avav read cycle time 250 ns r2 t avcl row address setup to r/c# low 50 ns r3 t clax row address hold from r/c# low 50 ns r4 t avch column address setup to r/c# high 50 ns r5 t chax column address hold from r/c# high 50 ns r6 t chqv r/c# high to output delay 2 150 ns r7 t glqv oe# low to output delay 2 50 ns r8 t phav rst# high to row address setup 1 s r9 t glqx oe# low to output in low z 0 ns r10 t ghqz oe# high to output in high z 50 ns r11 t qxgh output hold from oe# high 0 ns note: 1. see the ac input/output reference waveform for the maximum allowable input slew rate. 2. oe# may be delayed up to t chqv ? t glqv after the rising edge of r/c# without affecting t chqv . 3. t c = 0 c to + 85 c, 3.3 v 0.3 v v cc
intel ? 82802ab/ac firmware hub r 50 datasheet figure 14. a/a mux read timing diagram addresses (a) r/c# (c) v ih v il v ih v il row address stable column address stable we# (w) v ih v il oe# (g) v ih v il rp# (p) v ih v il data (d/q) v oh v ol high z high z data valid r7 r9 x x r8 r2 r5 r3 r4 r6 r1 r11 r10 x x next address stable
intel ? 82802ab/ac firmware hub r datasheet 51 6.4.4. a/a mux write operations (1,2) # symbol parameter notes min. max. units w1 t phwl rp# high recovery to we# low 1 s w2 t wlwh write pulse width low 100 ns w3 t dvwh data setup to we# high 1 50 ns w4 t whdx data hold from we# high 1 5 ns w5 t avcl row address setup to r/c# low 1 50 ns w6 t clax row address hold from r/c# low 1 50 ns w7 t avch column address setup to r/c# high 1 50 ns w8 t chax column address hold from r/c# high 1 50 ns w9 t whwl write pulse width high 100 ns w10 t chwh r/c# high setup to we# high 50 ns w11 t vpwh v pp1,2 setup to we# high 100 ns w12 t whgl write recovery before read 150 ns w13 t whrl we# high to ry/by# going low 0 ns w14 t qvvl v pp1,2 hold from valid srd, ry/by# high 0 ns note: 1. refer to table 6-28 [?] for valid a in and d in for block erase or program or other commands. 2. tc = 0 c to + 85 c, 3.3 v 0.3 v v cc
intel ? 82802ab/ac firmware hub r 52 datasheet figure 15. a/a mux write timing diagram addresses (a) r/c# (c) v ih v il v ih v il we# (w) v ih v il ry/by# (r) v ih v il v pp (v) v pph1,2 v il rp# (p) v ih v il r1 c1 r2 c2 oe# (g) v ih v il data (d/q) v oh v ol w5 w7 w6 w8 w10 w1 w2 w9 w3 w4 w11 w14 w12 w13 w15 valid srd d in d in a b c d e f note: a v cc power-up and stand-by b write block erase or program setup c write block erase confirm or valid address and data d automated erase or program delay e read status register data f ready to write another command
intel around the world united states and canada intel corporation robert noyce building 2200 mission college boulevard p.o. box 58119 santa clara, ca 95052-8119 usa phone: (800) 628-8686 europe intel corporation (uk) ltd. pipers way swindon wiltshire sn3 1rj uk phone: england (44) 1793 403 000 germany (49) 89 99143 0 france (33) 1 4571 7171 italy (39) 2 575 441 israel (972) 2 589 7111 netherlands (31) 10 286 6111 sweden (46) 8 705 5600 asia-pacific intel semiconductor ltd. 32/f two pacific place 88 queensway, central hong kong, sar phone: (852) 2844 4555 japan intel kabushiki kaisha p.o. box 115 tsukuba-gakuen 5-6 tokodai, tsukuba-shi ibaraki-ken 305 japan phone: (81) 298 47 8522 south america intel semicondutores do brazil rue florida, 1703-2 and cj22 cep 04565-001 sao paulo-sp brazil phone: (55) 11 5505 2296 for more information to learn more about intel corporation, visit our site on the world wide web at www.intel.com

▲Up To Search▲

Price & Availability of INTEL82802AC

	To Download INTEL82802AC Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .